home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950726-19950929
/
000108_news@columbia.edu_Tue Aug 8 01:59:38 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA06911
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Tue, 8 Aug 1995 10:37:46 -0400
Received: by apakabar.cc.columbia.edu id AA16837
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Tue, 8 Aug 1995 10:37:44 -0400
Path: news.columbia.edu!panix!news.mathworks.com!news.kei.com!nntp.et.byu.edu!news.byu.edu!hamblin.math.byu.edu!park.uvsc.edu!news.provo.novell.com!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit initialization on TCP/IP
Message-Id: <1995Aug8.075939.58350@cc.usu.edu>
Date: 8 Aug 95 07:59:38 MDT
References: <406ud5$am0@harbour.awod.com>
Organization: Utah State University
Lines: 48
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <406ud5$am0@harbour.awod.com>, chilton@awod.com (Carl Hilton) writes:
> I am having a heck of a time getting KERMIT to find my TCP/IP stack.
>
> On one machine I have FTP's PCTCP v2.1 running on a NOVELL network. The
>ODIPKE and ETHDRV are loaded by the network startup batch file.
>
> Now I want to run KERMIT. If I just run Kermit I get an 'unable to connect
> find TCP/IP stack or ODI packets'. I've tried loading the different
That's not a Kermit error message. Kermit error message
"Cannot attach to an Ethernet Packet Driver or a Novell ODI driver."
results when it can't find a packet delivery mechanism. If another stack is
running then that will yield this message from Kermit; see below on this
case.
(Carl, your mailer creates infinite length lines which don't match 80 column
equipment elsewhere; please press Enter before approaching the right edge, tnx.)
>ODIPKT.COM's that come with Kermit 3.14 but that does not help. In the
>NETWORKS/SETUP.DOC they talk about running through FTP's TNGLASS (tnglass
><host> <port> -c0 -e KERMIT.EXE) I've tried this and get dumped to the
>KERMIT prompt. Please help.
>
The Kermit documentation clearly says one can't run two protocol
stacks of the same kind together over the same board. That's the underlying
principle here. FTP Inc's stack counts as one, Kermit's internal stack
counts as one too.
MSK does run over TNGLASS. SET PORT BIOS<n> is the Kermit command
to use to find the Int 14h support provided by TNGLASS; don't use SET PORT
1 or COM1 because that tells Kermit to go to the serial port hardware. I
suspect there is a command in your setup to go to the hardware, and if so
then Kermit.exe command line phrase "-f NUL" is the way to avoid loading
mskermit.ini and other startup files. Reading the .ini files will reveal
if SET PORT x is present.
> On machine 2. I am running WFW3.11 with MS's TCPIP stack for WFW. I've
>tried shelling out to DOS and running WINPKT and even running WINPKT before
>I launch WFW but I keep getting the same error.
MS' TCP/IP stack isn't for DOS programs.
> Can someone plesase help.
What we do on my campus. Use Kermit's internal TCP/IP stack. Load
up ODIPKT + WINPKT before entering Windows. Use Kermit in a window of
Windows (that's Win 3.x and Win95). The one-stack-at-a-time rule still
applies.
Joe D.